System and method for processing a jackpot in a gaming system

ABSTRACT

A system and method for processing a jackpot in a gaming system. The gaming system has at least one gaming machine capable of issuing a jackpot. A host computer is coupled to the at least one gaming machine by a network. The remote system includes a remote device and a remote network interface coupled to the remote device for exchanging data between the host computer and the remote device The data includes jackpot information to process the jackpot.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims priority to U.S. ProvisionalApplication Serial No.(not assigned), filed Sep. 11, 2003 (AttorneyDocket No: 60518,169) and is a continuation-in-part application of U.S.patent application Ser. No. 09/967,571, filed Sep. 28, 2001.

FIELD OF THE INVENTION

[0002] The present invention relates generally to gaming machines, andmore particularly, to a system and method for remotely accessing theplayer tracking system.

BACKGROUND OF THE INVENTION

[0003] The growth and competition in the casino gaming market in recentyears and the increasingly sophisticated and complex technology beingintegrated into the gaming environment, at the individual game, casinomanagement, and auditing levels, presents both challenges andopportunities to game manufacturers, gaming establishment operators, andregulatory agencies. The technological capabilities and requirements of,for example, advanced electronic games, multi-site gaming operations,detailed player tracking, wide area progressive jackpots, and variousalternatives to the use of currency and coins by players, all present apotentially huge pool of ever-changing data which can be of great valueto casino operators (from a management standpoint) and to regulatorsfrom an audit/compliance standpoint.

[0004] Players may also be given an incentive through a player trackingclub. Usually, a player is identified during play by a player trackingID card and/or a player identification number (PIN). The player trackingsystem tracks the player's play and awards player tracking pointsaccording to established criteria. The player tracking points may beredeemed for prizes, such as complimentary meals or merchandise.

[0005] Typically, the player tracking system is accessed at workstationor computers which are linked to a remote server. The computerapplications which are used to access the player tracking system forvarious functions are stored on the workstation.

[0006] However, these types systems are inflexible and do not providethe casino operator with the maximum benefit and advantages availablefrom the information and systems now available.

[0007] The present invention is aimed at one or more of the problems asset forth above.

SUMMARY OF THE INVENTION

[0008] In one aspect of the present invention, a remote system for usewith a gaming system is provided. The gaming system has at least onegaming machine capable of issuing a jackpot. A host computer is coupledto the at least one gaming machine by a network. The remote systemincludes a remote device and a remote network interface coupled to theremote device for exchanging data between the host computer and theremote device. The data includes jackpot information to process thejackpot.

[0009] In another aspect of the present invention, a method forprocessing a jackpot for use with a gaming system, is provided. Thegaming system includes at least one gaming machine capable of issuing ajackpot. The method includes the steps of sending a selectable form to aremote device and filling out the form with data, by a user, on theremote device for processing the jackpot.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Other advantages of the present invention will be readilyappreciated as the same becomes better understood by reference to thefollowing detailed description when considered in connection with theaccompanying drawings wherein:

[0011]FIG. 1 is a block diagram of a remote system for use with a gamingsystem, according to an embodiment of the present invention;

[0012]FIG. 2 is block diagram of an gaming machine and a remote device,according to an embodiment of the present invention;

[0013]FIG. 3 is a more detailed block diagram of the remote device ofFIG. 2 and a computer program application, according to an embodiment ofthe present invention;

[0014]FIG. 4 is a block diagram of a web client operating on the remotedevice of FIG. 2, according to an embodiment of the present invention;

[0015]FIG. 5A is a first flow diagram of a method for enrolling a playerin a player tracking system, according to an embodiment of the presentinvention;

[0016]FIG. 5B is a second flow diagram of a method for enrolling aplayer in a player tracking system, according to a second embodiment ofthe present invention;

[0017]FIG. 6 is a diagrammatic illustration of a remote player signupform according to an embodiment of the present invention;

[0018]FIG. 7A is a first flow diagram of a method for remotely accessingplayer information, according to an embodiment of the present invention;

[0019]FIG. 7B is a second flow diagram of a method for remotelyaccessing player information, according to a second embodiment of thepresent invention;

[0020]FIG. 8 is a diagrammatic illustration of a remote playerinformation screen, according to an embodiment of the present invention;

[0021]FIG. 9A is a first flow diagram of a method for remotely accessinginformation related to a device, according to an embodiment of thepresent invention;

[0022]FIG. 9B is a second flow diagram of a method for remotelyaccessing information related to a device, according to a secondembodiment of the present invention;

[0023]FIG. 10 is a diagrammatic illustration of a remote assetinformation screen, according to an embodiment of the present invention;

[0024]FIG. 11A is a first flow diagram of a method for remotelyprocessing jackpot tickets, according to an embodiment of the presentinvention;

[0025]FIG. 11B is a second flow diagram of a method for remotelyprocessing jackpot tickets, according to a second embodiment of thepresent invention;

[0026]FIG. 12 is a diagrammatic illustration of a cash ticketinformation screen, according to an embodiment of the present invention;

[0027]FIG. 13A is a first flow diagram of a method for remotelyprocessing jackpot tickets, according to an embodiment of the presentinvention;

[0028]FIG. 13B is a second flow diagram of a method for remotelyprocessing jackpot tickets, according to a second embodiment of thepresent invention;

[0029]FIG. 14A is a diagrammatic illustration of a jackpot informationscreen, according to an embodiment of the present invention;

[0030]FIG. 14B is a diagrammatic illustration of a fill informationscreen, according to an embodiment of the present invention;

[0031]FIG. 15A is a first flow diagram of a method for remotelyprocessing hopper fills, according to an embodiment of the presentinvention;

[0032]FIG. 15B is a second flow diagram of a method for remotelyprocessing hopper fills, according to a second embodiment of the presentinvention;

[0033]FIG. 16A is a diagrammatic illustration of a hopper fillinformation screen, according to an embodiment of the present invention;

[0034]FIG. 16B is a diagrammatic illustration of a fill informationscreen according to an embodiment of the present invention;

[0035]FIG. 17A is a first flow diagram of a method for remotelyproviding a table rating interface, according to an embodiment of thepresent invention;

[0036]FIG. 17B is a second flow diagram of a method for remotelyproviding a table rating interface, according to a second embodiment ofthe present invention;

[0037]FIG. 18A is a diagrammatic illustration of an open table ratingscreen, according to an embodiment of the present invention;

[0038]FIG. 19A is a first flow diagram of a method for remotelyproviding an attendance interface, according to an embodiment of thepresent invention;

[0039]FIG. 19B is a second flow diagram of a method for remotelyproviding an attendance interface, according to a second embodiment ofthe present invention;

[0040]FIG. 20 is a diagrammatic illustration of a player attendanceinformation screen, according to an embodiment of the present invention;

[0041]FIG. 21A is a first flow diagram of a method for remotelyproviding a surveillance interface, according to an embodiment of thepresent invention;

[0042]FIG. 21B is a second flow diagram of a method for remotelyproviding a surveillance interface, according to a second embodiment ofthe present invention;

[0043]FIG. 22 is a diagrammatic illustration of an alert informationscreen, according to an embodiment of the present invention;

[0044]FIG. 23A is a flow diagram of a first method for adjusting pointsassigned to a player in a player tracking system, according to anembodiment of the present invention;

[0045]FIG. 23B is flow diagram of a second method for adjusting pointsassigned to a player in a player tracking system, according to anotherembodiment of the present invention;

[0046]FIG. 24 is a diagrammatical illustration of a point adjustmentrequest form, according to an embodiment of the present invention;

[0047]FIG. 25A is a flow diagram of a method for issuing vouchers to aplayer, according to an embodiment of the present invention;

[0048]FIG. 25B is a flow diagram of a second method for issuing vouchersto a player, according to another embodiment of the present invention;

[0049]FIG. 26 is a diagrammatic illustration of a voucher informationscreen, according to an embodiment of the present invention;

[0050]FIG. 27A is a flow diagram of a method for redeeming printedvouchers using a remote device, according to an embodiment of thepresent invention;

[0051]FIG. 27B is a flow diagram of a second method for redeemingprinted vouchers using a remote device, according to an embodiment ofthe present invention;

[0052]FIG. 28 is a diagrammatic illustration of a voucher informationform, according to an embodiment of the present invention;

[0053]FIG. 29A is a first flow diagram of a method for displaying a listof outstanding vouchers for a selected player, according to a firstembodiment of the present invention;

[0054]FIG. 29B is a second flow diagram of a method for displaying alist of outstanding vouchers for a selected patron, according to asecond embodiment of the present invention; and

[0055]FIG. 30 is a diagrammatic illustration of a voucher informationdialogue, according to an embodiment of the present invention.

DETAILED DESCRIPTION OF INVENTION

[0056] I. Overview

[0057] With reference to the drawings and in operation, the presentinvention provides a system 10 and methods related to a player trackingmethod or to one or more gaming devices 12.

[0058] The gaming devices 12 may be electronic or electric gamingmachines 13, such as slot or video slot machines, poker or video pokermachines, arcade or video arcade games, and the like, but may alsoinclude other types of devices 12A connected to the system 10, such asvirtual gaming machines (for online gaming), electronic interfaces foruse with table games, vending machines, token or credit dispensingmachines, ticket redemption machines, or any other electric orelectronic device connected to the network.

[0059] II. The Gaming System

[0060] In one embodiment, the system 10 and methods may be embodied orimplemented via an entertaining management and monitoring system orgaming system 14 which is shown in block diagram form in FIG. 1. Theentertainment and monitoring system 14 may include may additionalfunctions such as, real-time multi-site, slot accounting, playertracking, cage credit and vault, sports book data collection, Point ofSale (POS) accounting, keno accounting, bingo accounting, and table gameaccounting, a wide area progressive jackpot, and electronic fundstransfer (EFT). Two exemplary systems are disclosed in U.S. patentapplication Ser. No. 09/967,571. filed Sep. 28, 2001, and U.S.Provisional Patent Application Serial (Not Assigned), filed Sep. 11,2003 (Attorney Docket No. 60,518-169), both of which are herebyincorporated by reference.

[0061] In the illustrated embodiment, the system 10 includes eightelectronic gaming machines 13A-13H. However, it should be noted that thepresent invention is not limited to any number of devices 12 or machines13. In one embodiment, the machines 13 are organized into banks (notshown), each bank containing a plurality of machines 13.

[0062] The gaming devices 12 are connected via a network 16 to one ormore host computers 18, which are generally located at a remote orcentral location. The computer 18 includes a computer programapplication 20 which maintains one or more databases 22. In oneembodiment, the database(s) are Oracle database(s).

[0063] The computer program application 20 and databases 22 may be usedto record, track, and report accounting information regarding the gamingdevices 12 and/or users of the gaming devices 12 or players of theelectronic gaming machines 13. Additionally, the computer programapplication 20 and databases 22 may be used to maintain informationrelated to player tracking accounts (see below).

[0064] In general, the electronic gaming machines 13 are playable by aplayer 24. The player 24 may select one of the electronic gamingmachines 13C to play and insert a coin, credit, coupon, and/or playertracking card (not shown) into the chosen gaming machine 13C. Generally,the electronic gaming machines 13C have an associated number of creditsor coins required in order to play. In the case of video slot or pokergames, the game is played and an award in the form of credits may beawarded based on a pay table of the gaming machine 13.

[0065] With reference to FIG. 2, a block diagram of a suitableelectronic gaming machine 13C is shown.

[0066] The machine 13C comprises a game controller 26, or centralprocessing unit (CPU), a coin-bill management device 28, a displayprocessor 30, a RAM 32 as a memory device and a ROM 34 (generallyprovided as an EPROM). The CPU 26 is mainly composed of a microprocessorunit and performs various calculations and motion control necessary forthe progress of the game. The coin-bill management device 28 detects theinsertion of a coin or a bill and performs a necessary process formanaging the coin and the bill. The display processor 30 interpretscommands issued from the CPU 26 and displays desirable images on adisplay 36. The RAM 32 temporarily stores programs and data necessaryfor the progress of the game, and the ROM 34 stores, in advance,programs and data for controlling basic operation of the machine 12C,such as the booting operation thereof, game code and graphics.

[0067] Input to the gaming device 12C may be accomplished via mechanicalswitches or buttons or via a touchscreen interface (not shown). Suchgaming machines 12 are well known in the art and are therefore notfurther discussed.

[0068] The player 24 is identified via the player tracking card and/or aplayer identification number entered into player tracking device 38 ateach gaming machine 12 (see below). Player tracking accounts may beused, generally, to provide bonuses to a player, in addition to theaward designated by, in the case of a video slot or poker machine, thegaming machine's 12 paytable. These bonuses may be awarded to the player24 based a set of criteria, including, but not limited to, a) theplayer's play on the machine 12C, b) the player's overall play, c) playduring a predetermined period of time, and d) the player's birthday oranniversary, or e) any other definable criteria. Additionally, bonusesmay be awarded on a random basis, i.e., to a randomly chosen player orrandomly chosen game 12. Bonuses may also be awarded in a discretionarymanner or based on other criteria, such as, purchases made at a giftshop or other affiliated location.

[0069] In one embodiment, the player tracking device 38 includes aprocessor 40, a player identification card reader 42 and/or a numerickeypad 44, and a display 46. In one embodiment, the display 46 is atouchscreen panel and the numeric keypad 44 is implemented thereon.

[0070] The player 24 may be identified by entry of a player trackingcard into the player identification card reader 42 and/or entry of aplayer identification number (PIN) on the numeric key pad 46. The playtracking device 38 may also be used to communicate information betweenthe computer 18 and the corresponding gaming machine 12C. The playertracking device 40 may also be used to track bonus points, i.e.,incentive points or credits, downloaded from the computer 18.

[0071] In one aspect of the present invention, the bonuses are awardedas bonus points. In one embodiment, the bonus points are incentivepoints. In another embodiment, the bonus points are credits.

[0072] The incentive points may converted to credits using apredetermined ratio. The predetermined ratio may be 1 or any otherdesired ratio. The predetermined ratio may also be varied based ondetermined criteria, e.g., the gaming machine 12 being played, theplayer, or the time of day. Incentive points may be designated ascashable or non-cashable. The incentive points in a player account maybe downloaded to one of the gaming machines 12 for play.

[0073] III. Remote System

[0074] Returning to FIG. 1, the present invention provides a remotesystem 48 for use with the gaming system 14. The remote system 48provides access to various features or functions of the gaming system 14by one or more remote devices 50.

[0075] In the illustrated embodiment, there are four remote devices 50A,50B, 50C, 50D, however, this is for discussion purposes only. Any numberof remotes devices 50 may be included.

[0076] The remote devices 50 are connected to the network 16 through anetwork link 52. In one aspect of the present invention, the networklink 52 is a wireless connection. In one embodiment, the wirelessconnection uses the IEEE 802.11 standard, e.g., 802.11b or 802.11g.However, it should be noted that wireless links using other standardsmay also be used where appropriate, such as a short range radio link(e.g., a link using the technology known as “Blue Tooth”). In anotheraspect of the present invention, the network link 52 may be a wire link.

[0077] The remote devices 50 are generally used by a user 54 andprovides, as discussed below, access to various data and/or functions ofthe gaming system 14.

[0078] In one aspect, the user 54 is an employee of the gamingestablished where the gaming system 14 is operating. Typically, the user54 has an assigned role (or type) based on their job description.Typical roles may include, but are not limited to, system administrator,supervisor, pit, pit manager, slot floor employee, patron host, player'sclub, security, security supervisor, slot attendant, slot director, slotshift supervisor, slot technician, sports and racebook, surveillance,and table supervisor.

[0079] In one embodiment of the present invention, the remote devices 50provides access to one or more types of data and/or one or morefunctions based on the assigned role of the user 54. In one embodiment,a remote device 50 may provide access to one or more of the followingfunctions: remote patron signup, remote patron information, remotedevice information, remote cash ticket processing, remote jackpot ticketprocessing, remote hopper fill ticket processing, remote table ratinginterface, remote attendance, remote surveillance, adjusting a player'sbonus or comp points, issuing comp vouchers to a player, redeemingprinted vouchers, listing and redeeming outstanding vouchers assigned toa player, and retrieving and displaying information related to aspecific remote device 50. Each of these functions is described morefully below.

[0080] In one embodiment of the present invention, the remote device 50Amay be a mobile computer based on the PALM operating system or MicrosoftWindows operating system. With specific reference to FIG. 3 in oneembodiment of the present invention, the remote device 50A includes aprocessor 58, a memory 60 for storing applications and data, and adisplay 64. The display 64 may be a touchscreen display. The remotedevice 50A may also include a bar code reader 66. The bar code reader 66may be used to read a player ID card number from the ID card or to reada device ID number from a device 12 (see below). One such mobilecomputer is available from Symbol Technologies, Inc. of Holtsville, N.Y.as model number SPT 1800.

[0081] Additionally or alternatively, the remote device 50A may includean ID card reader 62 capable of reading magnetic stripe ID cards.

[0082] In another embodiment, the remote devices 50 are desktop, laptop,notebook, and/or sub-notebook computers.

[0083] Returning to FIG. 3, in one embodiment of the present invention,the remote device 50A includes a web client 56 which is stored in thememory 60 and run on the processor 58. The web client 56 is connected tothe computer program application 20 running on the host computer 18through the network link 52.

[0084] In one aspect of the present invention, all interaction with theuser, including the display of data and queries and the input of data,is handled by the web client 56. The web client 56 is responsible foracquiring user input, e.g., through forms, and formatting and presentinginformation to the user 54. The web client 56 is a computer applicationwhich is accessed via a web browser, such as Microsoft InternetExplorer, available from Microsoft Corp., of Redmond Calif. The webclient 56 may be written in Hypertext Mark-Up Language (HTML) andinclude one or more servlets (see below) which may be written in acomputer programming language, such as Java.

[0085] As shown in FIG. 3, the computer program application 20implements a remote network interface 66. The remote network interface68 couples the web client 56 with the database 22. In one embodiment,the remote network interface 68 obtains data from the database 22,formats the data, e.g., into an HTML response, and returns the formatteddata to the web client 56.

[0086] In one aspect of the present invention, the remote networkinterface 68 is coupled to the database 22 by one or more data objects70. In one embodiment, data is stored in the database 22 in data tables.The data objects 70 handle requests from the remote network interface68, abstracts the required data from the database tables and/or setsdata into the database tables.

[0087] As shown, in FIG. 3, the data objects 70 include a plurality offirst data object (DBOBJECTS) 76, at least one second data object(VDBOBJECTS) 74, and a third data object (BUSINESS OBJECT) 72.

[0088] The first data objects 76 are coupled to the database tables andabstract specific database tables for the at least one second dataobject 74. The first data objects 76 handle retrieving and setting datainto specific database tables.

[0089] The at least one second data object 74 is coupled to the firstdata objects 76 assemble multiple first data objects 76 into a singlethird data object 72. The at least one second data object 74 abstractthe third data object 72 from the database tables.

[0090] The third data object 72 is coupled to the at least one seconddata object 74. The third data object receives queries from the remotenetwork interface, retrieves responsive data from the database (throughthe first and second data objects 74, 76), formats the responsive dataand returns the responsive data to the remote network interface.

[0091] With reference to FIG. 4 in one embodiment, the web client 56 iswritten in HTML. In the illustrated embodiment, the web client 56includes a form layer 78, a menu layer 80, a login layer 82, and aservlet layer 84.

[0092] The login layer 82 provides security. It allows the user 54 tologon to the remote system 48. In one embodiment, the user 54 enters aname and password to logon. The user 54 may also be required to enter orselect the site at which the user 54 is located.

[0093] The menu layer 90 allows the user 54, once logged on, to navigateto and between servlets. The servlets are downloaded to the remotedevice 50 from the hose computer 18 as needed. The menu layer 90 alsohandles providing access to those servlets to which the user 54 hasaccess, typically based on an assigned role (see above).

[0094] The form and servlet layers 78, 84 provides common functionalityfor the servlets.

[0095] A. Remote Player or Patron Signup

[0096] With reference to FIGS. 5A, 5B, and 6, the remote system 48 theuser 54, such as a slot floor employee or patron host to quickly andremotely enroll a player or patron in the player tracking system. Theuser 54 will generally have a number of unassigned player ID cards (notshown). The user 54 may be approached by a player 24 who requests toenroll or may approach the player 24 and ask if they would want toenroll.

[0097] If the player 24 wants to enroll, the user 54 enters sign-upinformation or data onto the remote device 50A and gives the player 24 aplayer ID card. The sign-up information is sent by the remote device 50Ato the host computer 18 and stored in the database 22 along with the IDcard number of the assigned player ID card.

[0098] In one embodiment, the user 54 navigates to a servlet forenrolling the player 24 using the menu layer 80. The menu layer 80requests the servlet from the host computer 18 from which it is thendownloaded to the remote device 50A.

[0099] In one embodiment, only the player's name and a playeridentification number (PIN) is required. The player identificationnumber may be selected by the player 24 or be a temporary default PINassigned to the player ID card. The player ID card number to be assignedto the player 24 may be read by the ID card reader 62 or the barcodereader 66, as appropriate.

[0100] When the user 54 selected enrollment from the menu layer, the webclient 56 relays the request to the remote network interface 68. Theremote network interface 68 retrieves a signup form and sends the signupform to the remote device 50A for display and interaction with the user54 via the web client 56.

[0101] With specific reference to FIG. 5A, a first method 88 forenrolling the player 24 in the player tracking system using the remotedevice 50A, according to a first embodiment of the present invention isshown. In a first step 90, a fillable signup form is sent to the remotedevice 50A. In a second step 92, the player information (or enrollmentdata) is entered on the signup form via the remote device 50A.

[0102] With specific reference to FIG. 5B, a second method 94 forenrolling the player 24 in the player tracking system using the remotedevice 50A, according to a second embodiment of the present invention isshown.

[0103] In a first step 96, the signup form is displayed on the remotedevice 50A. In a step 98, if all required information, e.g., a zip code,was entered then the method 94 proceeds to a third step 100. If allrequired information was not entered, then an error message is displayedin a fourth step 102 and the process returns to the first step 96.

[0104] In the third step 100, the zip code is processed, i.e., thecorresponding city and state are determined. In a fifth step 104, if thezip code is not valid, then the method 94 displays an error message(fourth step 102). If the zip code is valid, then the method 94 proceedsto a sixth step 106.

[0105] In the sixth step 106, the enrollment data is stored are storedas records in the database 22 and control proceeds to a seventh step108. In the seventh step 108, if a room number, i.e., the hotel roomhotel in which the player 24 is residing was entered, then the processproceeds to an eighth step 110. Otherwise, the method 96 returns to thefirst step 96.

[0106] In the eighth step 110, an external system (not shown), may benotified for the creation of room lock keys. One such system In oneembodiment as discussed below, the room lock keys may be used for theplayer tracking system and/or room locks.

[0107] An exemplary signup form 110, displayed on the remote device 50Aby the web client 56 is shown in FIG. 6. As discussed above, in oneembodiment the only information required is the player's name and a PINnumber. The exemplary signup form 110 includes an entry box for theplayer's first, middle, and last names 112, 114, 116 and a PIN entry box118. After the required information has been entered, the user 54selects a save player button 120 to send the data to the host computer18.

[0108] In another embodiment, the signup form 110 requires additionalinformation. The additional information may include, but is not limitedto the following: player ID card number (from pre-printed card or leftblank for system generated card), address, zip code, country, telephonenumber(s), room number, number of adult cards, number of child cards,signup date, and one or more notes. Child cards operate only the lock ofa hotel room. Adult cards work in the player tracking system and operatethe room lock.

[0109] Additionally as discussed above, the display 46 is a touchscreendisplay. In one embodiment, the display may capture a signature of theplayer 24. The player's signature may be also be sent to the hostcomputer 18 with the enrollment data and stored in the database 22.

[0110] B. Remote Patron Information

[0111] With reference to FIGS. 7A, 7B, and 8, the remote system 48 theuser 54, such as a slot floor employee or patron host to quickly andremotely request and receive player information related to a specificplayer 24. This may be done prior to approaching the player 24 who isusing a specification gaming machine 13 or after the user 54 has beenapproached by the player 24.

[0112] In the illustrated embodiment, interaction with the user 54,including receiving input and displaying the player information, isaccomplished using the web client 56.

[0113] In one aspect of the present invention, the user 54 may identifythe player 24 through entry of the player's ID card number into theremote device 50A. In one embodiment, the ID card number may be enteredmanually. In another embodiment, the ID card number may be read from theplayer's ID card using the card reader 62 or the barcode reader 66 asappropriate.

[0114] In another aspect of the present invention, if the player 24 isutilizing one of the devices 12 and has identified themselves to theplayer tracking system by entry of the ID card into the device 12 and/orentered in their PIN number, the user 54 may identify the player 24 byentered a device ID number associated with the respective device 12. Asdiscussed below, the player tracking system has associated the ID numberof the device 12 with the player 24 while the player 24 is using thedevice 12. Thus, using the device ID number, the host computer 18 maydetermine the ID number of the player 24.

[0115] In one embodiment, the user 54 navigates to a servlet forrequesting player information using the menu layer 80. The menu layer 80requests the servlet from the host computer 18 from which it is thendownloaded to the remote device 50A.

[0116] The servlet displays a request form which is displayed to theuser 54. As discussed above, the user 54 may either enter the player IDcard number of the player 24 (manually or reading it from the ID card)or a device ID number associated with a device 12 being used by theplayer 24. The user 54 enters identification information (in the form ofthe player ID card number or the device ID number) which is returned tothe host computer 18 by the web client 56. The remote network interface68 receives the identification information, retrieves the playerinformation and returns the player information to the remote device 50Awhere it is displayed.

[0117] With specific reference to FIG. 7A, a first method 124 forremotely requesting information relating to a player 24 is provided. Ina first step 126, identification information is received at the remotedevice. In a second step 128, the identification information is receivedat the host computer. In a third step 130, the player information isretrieved from the database 22 as a function of the identificationinformation.

[0118] With specific reference to FIG. 7B, a second method 132 forremotely requesting player information using the remote device 50A isshown, according to a second embodiment of the present invention.

[0119] In a first step 134, the request form is displayed on the remotedevice 50A. In a second step 136, if a player ID card number has beenentered, then the method 132 proceeds to a third step 138. In the thirdstep 138, the ID card number is validated. In a fourth step 140, if theID card number is not valid, an error message is displayed in a fifthstep 142. If the ID card number is valid, then the message proceeds to asixth step 144.

[0120] In the sixth step 144, the query (request for player information)is processed by the host computer 18. The player (or patron) informationis then returned to the remote device 50A to be displayed in an seventhstep 146.

[0121] In the second step 136, if an ID card number has not beenentered, then the method 132 proceeds to an eighth step 148. In theeighth step 148, if a device (or asset) number has been entered, thenthe method 132 proceeds to a ninth step 150. If a device number has notbeen entered, then the method 132 proceeds to the fifth step 142 and anerror message is displayed.

[0122] In the ninth step 150, the device number is validated. In a tenthstep 152, if the device number is valid, then control proceeds to thefifth step 144. Otherwise, the method 132, proceeds to the fifth step142.

[0123] With specific reference to FIG. 8, in one embodiment the returnedplayer information is displayed on the remote device 50A in a playerinformation screen 152. In the illustrated embodiment, the playerinformation may include, but is not limited to, a player name, a playeraddress, a patron host name, at least one anniversary date, e.g.,birthday, wedding anniversary, sign-up date, any meters tracked by theplayer tracking system, such as bonus points (incentive points orcredits), jackpots, coin-out, coin-in, and win/(loss).

[0124] C. Remote Device Information

[0125] With reference to FIGS. 9A, 9B and 10, the remote system 48 theuser 54, such as a slot floor employee or a slot technician, to quicklyremotely request and receive asset or device information related to angaming device 12.

[0126] In the illustrated embodiment, interaction with the user 54,including receiving input and displaying the asset information isaccomplished using the web client 56.

[0127] In one aspect of the present invention, the user 54 may identifythe gaming device 12, such as an electronic gaming machine 13 byentering identification information. In one embodiment, theidentification information is an asset or device ID number. The IDnumber may be manually entered by the user 54. In another embodiment,the user 54 may use the barcode reader 66 to read a barcode, located onthe gaming device 12, containing the device ID number.

[0128] In one embodiment, the user navigates to a servlet for requesteddevice information using the menu layer 80. The menu layer 80 requeststhe servlet from the host computer 18 from which it is then downloadedto the remote device 50A.

[0129] The servlet displays a request form (not shown) which isdisplayed to the user 54. After the asset or device ID number entered,the ID number is sent to the remote network interface 68, which processthe query, and returns the requested device information to the remotedevice 50A where it is displayed.

[0130] With specific reference to FIG. 9A, a first method 154 forremotely requesting information related to a specific gaming device 12is provided. In a first step 156, identification information is receivedat the remote device 50A. In a second step 158, the identificationinformation is received at the host computer 18. In a third step 160,the device information is retrieved from the database 22 as a functionof the identification information.

[0131] With specification reference to FIG. 9B, a second method 162 isfor remotely requesting device information using the remote device 50Ais shown, according to an embodiment of the present invention.

[0132] In a first step 164, the request form is displayed on the remotedevice 50A. In a second step 166, if an asset number has been enteredthen the method 162 proceeds to a third step 170. Otherwise, an errormessage is displayed in a fourth step 168.

[0133] In the third step 170, the asset number is validated. In a fifthstep 172, if the asset number is valid then the method 162 proceeds to asixth step 174. In the sixth step 174, the query (request for assetinformation) is processed by the host computer 18. The device or assetinformation is returned to the remote device 50A to be displayed in aseventh step 176.

[0134] With specific reference to FIG. 10, in one embodiment thereturned asset information is displayed on the remote device 50A in aremote asset information screen 178. In the illustrated embodiment, theasset information may include, but is not limited to, an asset number, adevice number, a denomination (the base denomination the deviceaccepts), a manufacturer, a model, a master prom identifier, a game promidentifier, an online MAC address, an online TCP/IP address, a date onfloor, and any or all available system meters, such as, coin in, coinout, games player, and jackpots.

[0135] D. Remote Cash Ticket Processing

[0136] In one embodiment, a gaming system includes a gaming machine thatmay issue a cash ticket. The cash ticket is issued when a player electsto quit playing a particular gaming machine after accumulating a numberof credits. The number of credits is generally the sum of an originalnumber of credits, any downloaded credits, any inserted credits, and anywinnings (or losses).

[0137] With reference to FIGS. 11A, 11B and 12, the remote system 48allows the user 54, such as a slot floor employee or patron host toquickly and remotely process a cash ticket issued by a particular gamingmachine 13. The cash ticket issued by the gaming machine 13 includescash ticket information such as a cash ticket id and a value printed onthe cash ticket. The user 54 may be approached by a player 24 whorequests to cash out a cash ticket and receive the value of the cashticket.

[0138] If the player 24 wants to cash out, the user 54, via the remotedevice 50A, requests a cash ticket form. The remote network interface 68the cash ticket form to the remote device 50A.

[0139] When the user 54 selects the cash ticket form from the menu layer80, the web client 56 relays the request to the remote network interface68. The remote network interface 68 retrieves the cash ticket form andsends the cash ticket form to the remote device 50A for display andinteraction with the user 54 via the web client 56.

[0140] The cash ticket form may include a cash ticket button forselecting by the user 54 to communicate each step of the cash ticketprocessing that has occurred. For example, the cash ticket button is arequest button that the user 54 selects when the user 54 is approachedby the player 24. The cash ticket button may be an acknowledge buttonselected by the user 54 after validating the cash ticket and prior toprocessing the cash ticket. The cash ticket button may also be a processbutton selected by the user 54 after confirming that the cash ticket maybe paid. The cash ticket button may also be a paid button to confirmthat the user 54 has paid to the player 24 the value of the cash ticket.Each time the cash ticket button is selected by the user 54, the remotedevice 50A sends a notification of the event and the remote networkinterface 68 stores the notification in the host computer 18 which thenupdates the data in the database 23 relating to the status of the cashticket processing.

[0141] The cash ticket form may also include a field wherein the user 54enters the cash ticket id such as a number. The user 54 enters cashticket information or data onto the remote device 50A to verify that thecash ticket is valid and has not been previously processed. If the cashticket id is invalid or the cash ticket has already been processed, anerror message is displayed at the remote device 50A. The cash ticketinformation is sent by the remote device 50A to the host computer 18where cash ticket information is retrieved and sent back to the remotedevice 50A. In one embodiment, the cash ticket id is entered manually,then the user 54 selects a cash ticket entry button to send the cashticket form to the host computer 18. In another embodiment, the cashticket id is encoded in a barcode printed on the cash ticket. The barcode is read by the bar code reader and sent to the host computer 18.

[0142] In one embodiment, the user 54 navigates to a servlet 24 usingthe menu layer 80 for inputting and retrieving cash ticket information.The menu layer 80 requests the servlet from the host computer 18 fromwhich it is then downloaded to the remote device 50A.

[0143] After the validity of cash ticket is confirmed, the cash ticketinformation is retrieved from the database 22 by the remote networkinterface 68 and displayed to the user 54 at the remote device 50A. Withspecific reference to FIG. 12, in one embodiment the returned cashticket information is displayed on the remote device 50A in a cashticket information screen 196.

[0144] The cash ticket information includes ticket details 168, such asa gaming machine identifier. The gaming machine identifier includes agaming machine id and a gaming machine location to identify the gamingmachine issuing the cash ticket. The ticket details 168 further includea date identifier for identifying the issue date of the cash ticket, ashift identifier for identifying the work shift during which the cashticket was issued, and a value identifier for identifying the value ofthe cash ticket, thereby allowing the user 54 to confirm the valueprinted on the cash ticket and the value stored in the host computer 18.

[0145] With specific reference to FIG. 11A, a first method 170 forprocessing a cash ticket using the remote device 50A, according to afirst embodiment of the present invention is shown. In a first step 172,a fillable cash ticket form is sent to the remote device 50A. In asecond step 174, the cash ticket information is entered on the cashticket form via the remote device 50A.

[0146] With specific reference to FIG. 11B, a second method 176 forprocessing the cash ticket using the remote device 50A, according to asecond embodiment of the present invention is shown.

[0147] In a first step 178, the cash ticket form is displayed on theremote device 50A. In a second step 180 a cash ticket id is entered. Ina third step 182, the cash ticked id is verified. If the cash ticket idis invalid, then the method 176 proceeds to a fourth step 184. If thecash ticket id corresponds to a valid unprocessed cash ticket, then themethod 178 proceeds to a fifth step 186. In the fourth step 184, anerror message is displayed and the method 176 returns to the first step178.

[0148] In the fifth step 186, the ticket details are retrieved from thedatabase 22 and control proceeds to a seventh step 188. In the seventhstep 188, the ticket details are processed and display at the remotedevice 50A. The user 54 may then pay the player. As discussed above, theuser may be required to acknowledge through the selection of the cashticket button at each step. Once the user has acknowledged that theplayer has been paid,, the remote display displays a cash ticket paidmessage in an eighth step 190.

[0149] E. Remote Jackpot Ticket Processing

[0150] In one embodiment, a gaming system includes a gaming machine thatmay issue a jackpot ticket. In one embodiment, a jackpot ticket isissued by the gaming machine when a play of the game results in a winhaving an associated number of credits over a predetermined number ofcredits. Such a jackpot causes the gaming machine 12 to lock up, issuean alert and prevents the player from playing.

[0151] In another embodiment, the gaming machine 12 does not issuejackpot ticket. However, the user 54 may be required to go to the gamingmachine 12 to process the jackpot

[0152] With reference to FIGS. 13A, 13B and 14A, the remote system 48allows the user 54, such as a slot floor employee, to quickly andremotely process a jackpot issued by a particular gaming machine 13. Thejackpot issued by the gaming machine 13 has associated jackpotinformation such as a jackpot id and a value of the jackpot.

[0153] In one embodiment, the jackpot is dispensed by the gaming machine13, while jackpots above the threshold require interaction with anemployee, i.e., the user 54. Additionally, the jackpot maybe required tobe paid by a cashier. If a jackpot ticket has been issued, the user 54may be approached by a player 24 who requests to collect the value ofthe jackpot. Alternatively, the user 54 may have to travel to the gamingmachine 13 to process the jackpot.

[0154] If the player 24 wants to collect the jackpot, the user 54, viathe remote device 50A, requests a jackpot form (not shown). The remotenetwork interface 68 sends the jackpot form to the remote device 50A.

[0155] When the user 54 selects the jackpot form from the menu layer 80,the web client 56 relays the request to the remote network interface 68.The remote network interface 68 retrieves the jackpot form and sends thejackpot form to the remote device 50A for display and interaction withthe user 54 via the web client 56.

[0156] The jackpot form includes a jackpot button for selecting by theuser 54 to communicate each step of the jackpot processing that hasoccurred. For example, the jackpot button is a request button that theuser 54 selects when a jackpot is announced and the user 54 isapproached by the player 24 to collect the jackpot. The jackpot buttonmay be an acknowledge button selected by the user 54 after validatingthe jackpot and prior to processing the jackpot. The jackpot button mayalso be a process button selected by the user 54 after confirming thatthe jackpot may be paid. The jackpot button may also be a paid button toconfirm that the user 54 has paid to the player 24 the value of thejackpot. Each time the jackpot button is selected by the user 54, theremote device 50A sends a notification of the event and the remotenetwork interface 68 stores the notification in the host computer 18which then updates the data in the database 22 relating to the jackpotstatus in the jackpot processing.

[0157] In one embodiment, the jackpot form lists several fields havingjackpot information, including the jackpot identifier, fill detail andjackpot status, for all active jackpots. The user 54 may select eitherthe jackpot identifier or the jackpot status. If the user 54 selects thejackpot identifier, then jackpot detail is displayed on the remotedevice 50A. If the user 54 selects jackpot status, then the jackpotstatus advances to an advanced jackpot status, a notification is sent tothe host computer 18 to update the database 22 and the remote device 50Adisplays the updated jackpot status on the jackpot form.

[0158] In another embodiment, the jackpot form includes a field whereinthe user 54 enters the jackpot id such as a number. The user 54 entersjackpot information or data onto the remote device 50A to verify thatthe jackpot is valid and has not been previously processed. If thejackpot id is invalid or the jackpot has already been processed, anerror message is displayed at the remote device 50A. The jackpotinformation is sent by the remote device 50A to the host computer 18where jackpot information is retrieved and sent back to the remotedevice 50A.

[0159] In one embodiment, the jackpot id is entered manually, then theuser 54 selects a jackpot entry button to send the jackpot form to thehost computer 18. In another embodiment, the jackpot id is read by thebar code reader and sent to the host computer 18.

[0160] In one embodiment, the user 54 navigates to a servlet 24 usingthe menu layer 80 for inputting and retrieving jackpot information. Themenu layer 80 requests the servlet from the host computer 18 from whichit is then downloaded to the remote device 50A.

[0161] After the validity of jackpot is confirmed, the jackpotinformation is retrieved from the database 22 by the remote networkinterface 68 and displayed to the user 54 at the remote device 50A. Withspecific reference to FIG. 14A, in one embodiment the returned jackpotinformation is displayed on the remote device 50A in a jackpotinformation screen 238. With reference to FIG. 14B, in anotherembodiment, the returned fill information is displayed on the remotedevice 50A in a fill information screen 240.

[0162] The jackpot information includes fill detail 198, such as agaming machine identifier. The gaming machine identifier includes agaming machine id and a gaming machine location to identify the gamingmachine issuing the jackpot. The fill detail 198 further includes agaming date for identifying the issue date of the jackpot, a gamingshift for identifying the work shift during which the jackpot wasissued, and a jackpot value for identifying the value of the jackpot,thereby allowing the user 54 to confirm the value printed on the jackpotand the value stored in the host computer 18.

[0163] If the user 54 selects the jackpot identifier field on thejackpot form, jackpot detail 200 as a function of the jackpot identifieris retrieved from the host computer 18 and displayed at the remotedevice 50A. Jackpot detail 200 may include the gaming machine id and thegaming machine location to identify the gaming machine issuing thejackpot. The jackpot detail 200 may further include a gaming machinename for identifying the particular game issuing the jackpot, a gamingdenomination for identifying the particular type of credit issued, thegaming date for identifying the issue date of the jackpot, and thegaming shift for identifying the work shift during which the jackpot wasissued.

[0164] With specific reference to FIG. 13A, a first method 202 forprocessing a jackpot using the remote device 50A, according to a firstembodiment of the present invention is shown. In a first step 204, aselectable jackpot form is sent to the remote device 50A. In a secondstep 206, the jackpot information is entered on the jackpot form via theremote device 50A.

[0165] With specific reference to FIG. 13B, in another aspect of thepresent invention, a method 208 for displaying or processing jackpots isshown. In a first step 210, all pending jackpots are displayed. In oneembodiment, the list of pending jackpots includes at least a jackpot idand a jackpot status. In a second step 214, if the user 54 selectsjackpot id of a jackpot, the method 208 proceeds to a third step 222. Ifthe user 54 selects the jackpot status, the method 208 proceeds to afourth step 236. In the third step 222, jackpot details are displayed onthe remote device 50A. In the fourth step 236, the selected jackpot isprocessed by the user 54.

[0166] F. Remote Hopper Fill Ticket Processing

[0167] With reference to FIGS. 15A, 15B, 16A and 16B, the remote system48 allows the user 54, such as a slot floor employee to quickly andremotely process a hopper fills in a particular gaming machine 13, i.e.,insert credits or coins into the game machine's hopper to be dispensedto the player 24 when a jackpot has been won, when the game machine hasrun out or is low on credits. The number of credits remaining in thehopper (not shown) are tracked by the host computer 18 (or game machine13 and relayed to the host computer)which issues an alert when thenumber of credits remaining reaches a certain amount so that the hoppermay be restocked with credits such as coins, tokens, paper money, or thelike.

[0168] Once an alert is issued, the user 54, via the remote device 50A,may acknowledge the alert and request a hopper fill form (not shown).The remote network interface 68 sends the hopper fill form to the remotedevice 50A.

[0169] When the user 54 selects the hopper fill form from the menu layer80, the web client 56 relays the request to the remote network interface68. The remote network interface 68 retrieves the hopper fill form andsends the hopper fill form to the remote device 50A for display andinteraction with the user 54 via the web client 56.

[0170] In one embodiment, the hopper fill form includes a hopper fillbutton (not shown) for selecting by the user 54 to communicate each stepof the hopper fill processing that has occurred. For example, the hopperfill button is a request button that the user 54 selects when an alertis announced and the user 54 approaches the gaming machine 13 to processthe hopper fill. The hopper fill button may also be an acknowledgebutton selected by the user 54 after validating the hopper fill andprior to processing the hopper fill. The hopper fill button may also bea process button selected by the user 54 after confirming that thehopper is being restocked. The hopper fill button may also be a fillbutton to confirm that the user 54 has completed restocking the hopper.Each time the hopper fill button is selected by the user, the remotedevice 50A sends a notification of the event and the remote interfacestores the notification in the host computer 18 which then updates thedata in the database 22 relating to the credit status in the hopper fillprocessing.

[0171] In one embodiment, the hopper fill form lists several fieldshaving hopper fill information, including the hopper fill identifier,fill detail and credit status, for all active hopper fills. The user 54may select either the hopper fill identifier or the credit status. Ifthe user 54 selects the hopper fill identifier, then hopper fill detailis displayed on the remote device 50A. If the user 54 selects creditstatus, then the credit status advances to an advanced credit status, anotification is sent to the host computer to update the database and theremote device displays the updated credit status on the hopper fillform.

[0172] In another embodiment, the hopper fill includes a field whereinthe user 54 enters the hopper id, such as a number. The user 54 entershopper fill information or data onto the remote device 50A to verifythat the hopper id is valid and has not been previously processed. Ifthe hopper id is invalid or the hopper fill has already been processed,an error message is displayed at the remote device 50A. The enteredhopper fill information is sent by the remote device 50A to the hostcomputer 18 where additional hopper fill information is retrieved andsent back to the remote device 50A. In one embodiment, the hopper id isentered manually, then the user 54 selects a hopper fill entry button tosend the hopper fill form to the host computer 18. In anotherembodiment, the hopper id is read from a barcode on the hopper or on thegame machine 13 by the bar code reader 66 and sent to the host computer18.

[0173] In one embodiment, the user 54 navigates to a servlet 24 usingthe menu layer 80 for inputting and retrieving hopper fill information.The menu layer 80 requests the servlet from the host computer 18 fromwhich it is then downloaded to the remote device 50A.

[0174] After the validity of hopper is confirmed, the hopper fillinformation is retrieved from the database 22 by the remote networkinterface 68 and displayed to the user 54 at the remote device 50A. Withspecific reference to FIG. 16A, in one embodiment the returned hopperfill information is displayed on the remote device 50A in a hopper fillinformation screen 288. With reference to FIG. 16B, in anotherembodiment, the returned fill information is displayed on the remotedevice 50A in a fill information screen 290.

[0175] The hopper fill information includes fill detail 248, such as agaming machine identifier. The gaming machine identifier includes agaming machine id and a gaming machine location to identify the gamingmachine requiring the hopper fill. The fill detail 248 may furtherinclude a gaming date for identifying the issue date of the fill, agaming shift for identifying the work shift during which the fill wasissued, and/or a credit value for identifying the value of the creditssupplied.

[0176] If the user 54 selects the hopper fill identifier field on thehopper fill form, hopper fill detail as a function of the hopper fillidentifier is retrieved from the host computer 18 and displayed at theremote device 50A. In one embodiment, the hopper fill detail includesthe gaming machine id and the gaming machine location to identify thegaming machine requiring the credit or hopper fill. The hopper filldetail may further include a gaming machine game for identifying theparticular game issuing the credits, a gaming denomination foridentifying the particular type of credit issued, the gaming date foridentifying the fill date of the hopper, and/or the gaming shift foridentifying the work shift during which the hopper was filled.

[0177] With specific reference to FIG. 15A, a first method 252 forprocessing a hopper fill using the remote device 50A, according to afirst embodiment of the present invention is shown. In a first step 254,a selectable hopper fill form is sent to the remote device 50A. In asecond step 256, the hopper fill information is entered on the hopperfill form via the remote device 50A.

[0178] With specific reference to FIG. 15B, a second method 258 forprocessing the hopper fill using the remote device 50A, according to asecond embodiment of the present invention is shown.

[0179] In a first step 260, the remote device 50A displays selectablehopper fill information, including pending fills having a credit statusand hopper fill identifier. In an alternate embodiment, the hopper fillform or gaming machines 13 having hopper fill information, is displayedon the remote device 50A. In one embodiment, the hopper fill informationis selectable. In another embodiment the hopper fill information isfillable requiring credit refill.

[0180] In a second step 262, the user 54 selects a pending fill. If theuser 54 selects the hopper fill identifier, control proceeds to a thirdstep 264, the fill detail is displayed and control returns to the firststep 260. If the user 54 selects the credit status, then the creditstatus advances to an advanced credit status and control returns to thefirst step 260. If all required information was not entered, then anerror message is displayed and the hopper fill form is displayed again.

[0181] Then he hopper id is verified. If the hopper id is not valid,then the method 258 displays an error message (fourth step 266). If thehopper id is valid, then the fill detail is retrieved from the database22 and displayed at the remote device 50A.

[0182] After the hopper is filled with credits by the user 54, theremote display displays a credit filled message.

[0183] If the user selects another hopper fill identifier, the hopperfill detail is retrieved from the host computer and displayed on theremote device 50A.

[0184] If the user selects a credit status, the credit status advancesto an advanced credit status which is then displayed at the remotedevice 50A.

[0185] G. Remote Table Rating Interface

[0186] With reference to FIGS. 17A, 17B, and 18, the remote system 48allows the user 54, such as a slot floor employee or patron host, toquickly and remotely process a table rating and, send and receive tablerating information 450 related to a specific player 24. A table ratingallows the gaming system 10 to rate or rank the player 24 by determininghis or her given session or play, determine his or her worth to thecasino, and assign a point award.

[0187] In the illustrated embodiment, interaction with the user 54,including receiving input and displaying the player information, isaccomplished using the web client 56.

[0188] In one aspect of the present invention, the user 54 may identifythe player 24 through entry of the player's ID card number into theremote device 50A. In one embodiment, the ID card number may be enteredmanually. In another embodiment, the ID card number may be read from theplayer's ID card using the card reader 62 or the barcode reader 66 asappropriate.

[0189] In another aspect of the present invention, if the player 24 isutilizing one of the devices 12 and has identified themselves to thegaming system by entry of the ID card into the device 12 and/or enteredin their PIN number, the user 54 may identify the player 24 by enteringa device ID number associated with the respective device 12. Asdiscussed below, the gaming system has associated the ID number of thedevice 12 with the player 24 while the player 24 is using the device 12.Thus, using the device ID number, the host computer 18 may determine theID number of the player 24.

[0190] In one embodiment, the user 54 navigates to a servlet forrequesting player information using the menu layer 80. The menu layer 80requests the servlet from the host computer 18 from which it is thendownloaded to the remote device 50A.

[0191] The servlet displays a table rating form which is displayed tothe user 54. As discussed above, the user 54 may either enter the playerID card number of the player 24 (manually or reading it from the IDcard) or a device ID number associated with a device 12 being used bythe player 24. The user 54 enters the player information (in the form ofthe player ID card number or the device ID number) which is returned tothe host computer 18 by the web client 56. The remote network interface68 receives the player information, retrieves the table ratinginformation 450 and returns the table rating information 450 to theremote device 50A where it is displayed. With specific reference to FIG.18, in one embodiment the returned table rating information is displayedon the remote device 50A in an open table rating form screen 486.

[0192] When the player information is entered, the remote networkinterface 68 determines whether the information is valid. If valid, thetable rating information 450 is stored in or retrieved from the database22 as a function of the identification information. If invalid, an errormessage is displayed on the remote device 50A. The player information450 includes a player identifier such as a player number, player nameand address, and the like.

[0193] The purpose of the table rating information 450 is to registerand display a patron's risk or ranking at a particular gaming machine.The risk or ranking informs the user 54 about the player's 24 spendingor risk habits during a given session of play at a gaming machine.

[0194] The player information includes a table rating status of open orclosed for a particular gaming machine 13. If the status is open, theplayer is currently playing the particular gaming machine 13, therebyenabling the user to generate a table rating. When the player 24 decidesto discontinue playing, the user 54 swipes the player's 24 ID card andbrings up the table rating status in a closed status form (not shown)having fillable fields and a status button. The user 54 enters tablerating information about the session, including but not limited to theplayer name, the gaming machine 13, the gaming machine location, thetime the player 24 began play, the time the player 24 ceased play, theaverage bet by the player 24, and the amount won by the player 24 whenleaving the gaming machine 13. The user 54 selects the status button andthe table rating is established, sent to the database via the remotenetwork interface and stored therein. Thereafter, any remote devicesdisplaying a table rating form relating to the particular gaming machine13 displays the newly entered table rating information.

[0195] If, after swiping the player's card, the player 24 does not havean open table rating, an open table form is displayed on the remotedevice. The open table form is fillable by the user 54 with table ratingdetails which may include the player's name, the zone information(gaming machine location), a selectable list of the bank information(gaming machines 13) available at that location, a seat identifier atwhich the player 24 is seated, the estimated average bet by the player24, the bet value the player is opening the gaming machine 13 with. Thezone information entered by the user 54 may also include bankinformation as a function of the zone information. The bank informationassociated with the zone information is displayed and the user 54selects the appropriate banking information associated with theparticular gaming machine 13.

[0196] Once the information is entered, the user 54 selects the statusbutton to send and store the table rating details to the database 22 andupdate the table rating status to open. The updated table rating statusis sent to all remote devices displaying information for the particulargaming table. The update may be sent automatically or upon request.

[0197] With specific reference to FIG. 17A, a first method 452 forremotely requesting table rating information relating to a player 24 isprovided. In a first step 454, a fillable form is sent to a remotedevice for receiving table rating information. In a second step 456, thetable rating information is received at the host computer for processinga table rating for the player..

[0198] With specific reference to FIG. 17B, a second method 458 forremotely processing a table rating using the remote device 50A is shown,according to a second embodiment of the present invention.

[0199] In a first step 460, the table rating form is displayed on theremote device 50A.

[0200] In a second step, if a player ID card number is entered, then themethod proceeds to a third step. The table rating status is thenreturned to the remote device 50A to be displayed in the third step 464.

[0201] In a fourth step 466, if the table rating status is open, theclosed status form is displayed on the remote device.

[0202] In a fifth step 468, if the table rating is closed and controlreturns to the first step 460. In the third step 464, if the tablerating status is not open, then the method 458 proceeds to a sixth step470.

[0203] In the sixth step 470, the system determines if the remotenetwork interface is a casino. System view shows the zones of the systemand control proceeds to a seventh step 472. If the system view shows thezones then control proceeds to a seventh step 472, otherwise controlproceeds to a ninth step 476.

[0204] In the seventh step 472, zone information is displayed.

[0205] In an eighth step 474, zone is selected and control proceeds tothe ninth step 476.

[0206] In the ninth step 476, the system determines if the remotenetwork interface shows the zone view and control proceeds to a tenthstep 478.

[0207] If the system shows the zone view, then bank information is shownin the tenth step 478 and control proceeds to an eleventh step 480.Otherwise, control proceeds to a twelfth step 482.

[0208] In the eleventh step 480, a bank is entered, and control proceedsto the twelfth step 482.

[0209] In the twelfth step 482, the open rating form is displayed andcontrol proceeds to a thirteenth step 484.

[0210] In the thirteenth step 484, the user 54 enters table ratinginformation.

[0211] In the fourteenth step 486, the table rating is opened andcontrol returns to the first step 460.

[0212] H. Remote Attendance

[0213] With reference to FIGS. 19A, 19B, and 20, the remote system 48allows the user 54, such as a slot floor employee or patron host, toquickly and remotely request, send and receive player attendanceinformation 350 related to a specific player 24. For example, amarketing or special event may be targeted to patrons or players meetingdefined criteria. Each player who attends the event is identified astheir attendance is stored in the player tracking system.

[0214] In the illustrated embodiment, interaction with the user 54,including receiving input and displaying the player attendanceinformation, is accomplished using the web client 56.

[0215] In one aspect of the present invention, the user 54 may identifythe player 24 through entry of the player's ID card number into theremote device 50A. In one embodiment, the ID card number may be enteredmanually. In another embodiment, the ID card number may be read from theplayer's ID card using the card reader 62 or the barcode reader 66 asappropriate.

[0216] In another aspect of the present invention, if the player 24 isutilizing one of the devices 12 and has identified themselves to thegaming system by entry of the ID card into the device 12 and/or enteredin their PIN number, the user 54 may identify the player 24 by enteringa device ID number associated with the respective device 12. Asdiscussed below, the gaming system has associated the ID number of thedevice 12 with the player 24 while the player 24 is using the device 12.Thus, using the device ID number, the host computer 18 may determine theID number of the player 24.

[0217] In one embodiment, the user 54 navigates to a servlet forrequesting player attendance information using the menu layer 80. Themenu layer 80 requests the servlet from the host computer 18 from whichit is then downloaded to the remote device 50A.

[0218] The servlet displays an attendance form which is displayed to theuser 54. As discussed above, the user 54 may either enter the player IDcard number of the player 24 (manually or reading it from the ID card)or a device ID number associated with a device 12 being used by theplayer 24. The user 54 enters identification information (in the form ofthe player ID card number or the device ID number) which is returned tothe host computer 18 by the web client 56. The remote network interface68 receives the identification information, retrieves the playerattendance information 350 and returns the player attendance information350 to the remote device 50A where it is displayed. With specificreference to FIG. 20, in one embodiment the returned player attendanceinformation is displayed on the remote device 50A in an playerattendance information screen 384.

[0219] When the identification information is entered, the remotenetwork interface 68 determines whether the identification is valid. Ifvalid, the gaming machine information is stored in or retrieved from thedatabase 22 as a function of the identification information. If invalid,an error message is displayed on the remote device. 50A. The gamingmachine information includes a device identification number, and theplayer attendance information is retrieved from the database 22 as afunction of the device identification number. The player attendanceinformation 350 includes a player identifier such as a player number,player name and address, and the like. The player attendance information350 includes a gaming machine identifier which indicates what gamingmachines the player 24 has attended on a particular day.

[0220] The purpose of the player attendance information 350 is toregister and display a patrons attendance at a particular gaming machineor marketing event. Attempting to register a player 24 alreadyregistered will generate and display an error.

[0221] With specific reference to FIG. 19A, a first method 352 forremotely requesting information relating to a player 24 is provided. Ina first step 354, identification information is received at the remotedevice. In a second step 356, the identification information is receivedat the host computer. In a third step 358, identification information isstored in the database, i.e., the player before is marked as the playerattending the event. In a fourth step 360, the player attendanceinformation is retrieved from the database 22 as a function of theidentification information.

[0222] With specific reference to FIG. 19B, a second method 362 forremotely requesting player information using the remote device 50A isshown, according to a second embodiment of the present invention.

[0223] In a first step 364, the attendance form is requested by the user54 on the remote device 50A.

[0224] In a second step 366, the user 54 selects and enters an event orgaming via machine and control proceeds to a fourth step 370.

[0225] In a third step 368, an error message is displayed if the userdoes not enter or select an event and control returns to the first step364.

[0226] In the fourth step 370, if a player ID card number is entered,then the method 362 proceeds to a fifth step 372.

[0227] In the fifth step 372, the ID card number is validated.

[0228] In a sixth step 374, if system determines if the ID card numberis not valid, and control proceeds to the third step 368 where an errormessage is displayed. If the ID card number is valid, then the methodproceeds to a seventh step 376.

[0229] In the seventh step 376, if the player 24 is not marked asattending the event, the control proceeds to an eighth step 378.

[0230] In the eight step 378, the player's attendance at the gamingmachine is registered by the system, and control returns to the firststep 264.

[0231] I. Remote Surveillance

[0232] With reference to FIGS. 21A, 21B, and 22, the remote system 48allows the user 54, such as a slot floor employee or patron host toquickly and remotely process an alert having data including user roleinformation, alert information and alert detail issued by a gamingmachine 13. The user role information is a system where each user 54 isassigned a role in a hierarchy of roles. The user's role and level onthe hierarchy determines which functions and information the user canaccess and the operations the user can perform.

[0233] In the illustrated embodiment, interaction with the user 54,including receiving input and displaying the alert information, isaccomplished using the web client 56.

[0234] In one aspect of the present invention, an alert form displaysall active alerts and displays the alerts on the remote device 50A in analert form as a function of the user role information. The alert formdisplays the alert and the date and time it occurred. The user 54 mayidentify the alert and select the alert via an alert button toacknowledge that the user 54 is addressing the alert and will clear thealert after it is addressed. After the user 54 addresses the alert andacknowledges that it is addressed, the database 22 is updated and thealert form is refreshed with updated alert information.

[0235] In the illustrated embodiment, the user 54 selects the alert fromthe alert form and alert details 300 are displayed. The alert detailsmay include, but are not limited to, an alert type for describing thealert and an alert date for describing the date and time that the alertoccurred. The alert details 300 may further include a device identifierfor describing the gaming device the alert occurred on, a zone name fordescribing the zone of the gaming floor that the device is located in,and a bank name for describing the bank of the gaming floor that thedevice is located in. Additional alert details 300 may include arepository identifier for describing the repository the alert occurredon, a document identifier for describing a document created by thealert, an alert value for describing the value of the alert, and analert point describing the point value of the alert. The alert details300 may also further include an employee identifier for describing theemployee that initiated the alert and an alert message providing a textdescription of the alert.

[0236] In one embodiment, the user 54 navigates to a servlet forrequesting alert information using the menu layer 80. The menu layer 80requests the servlet from the host computer 18 from which it is thendownloaded to the remote device 50A.

[0237] In one embodiment, the servlet displays the alert form which isdisplayed to the user 54. As discussed above, the user 54 may select thealert displayed on the alert form to retrieve the alert detail 300 whichis returned to the host computer 18 by the web client 56. The remotenetwork interface 68 receives the alert information, retrieves the alertdetail 300 and returns the alert detail 300 to the remote device 50Awhere it is displayed. With specific reference to FIG. 22, in oneembodiment the returned alert information is displayed on the remotedevice 50A in an alert information screen 330.

[0238] With specific reference to FIG. 21A, a first method 302 forremotely processing an alert is provided. In a first step 304, alertinformation is received at the remote device. In a second step 306, theuser selects the alert. In a third step 308, the alert information isretrieved from the database 22 as a function of the selected alert.

[0239] With specific reference to FIG. 21B, a second method 310 forremotely requesting player information using the remote device 50A isshown, according to a second embodiment of the present invention.

[0240] In a first step 312, the alert information is retrieved as afunction of the user role.

[0241] In a second step 314, the retrieved alert information isdisplayed on the remote device 50A.

[0242] In a third step 316, the user selects an alert, then the method310 proceeds to a fourth step 318.

[0243] In the fourth step 318, alert detail is retrieved and displayedas a function of the selected alert.

[0244] In a fifth step 320, the user selects an alert button forrefreshing the alert information stored in the system 10.

[0245] In a sixth step 322, the user acknowledges the alert.

[0246] In a seventh step 324, the system determines if the alert hasalready been acknowledged.

[0247] In an eighth step 326, if the alert was previously acknowledged,an error message is displayed and the method returns to the first step312. If the acknowledgement is valid, then the message proceeds to theninth step 328.

[0248] In the ninth step 328, the alert is processed by the hostcomputer 18, notification is sent to other processes in the system,including the database and control returns to the first step 312.

[0249] In the third step 316, the user selects the alert button torefresh the alert information displayed at the remote device 50A.

[0250] Obviously, many modifications and variations of the presentinvention are possible in light of the above teachings. The inventionmay be practiced otherwise than as specifically described within thescope of the appended claims.

[0251] J. Patron Point Adjustment

[0252] With reference to FIGS. 23A, 23B and 24, the remote devices 50allow a user 54 to display and/or increase a player's point, e.g., bonuspoints, or comp point balance. In one embodiment, the remote networkinterface 68 exchanges data between the host computer 18 and the remoterdevice 50. The data includes adjustment information to adjust the pointsassociated with a player 24 in the player tracking system.

[0253] In one embodiment, the data includes a point management form (notshown) which is sent from the remote network interface 68 to the remotedevice 50A. The point management form is fillable with playerinformation by the user 54. The remote device 50 sends the playerinformation to the remote network interface 68. Once the player 24 hasbeen identified, the remote network interface 68 sends a pointadjustment request from to the remote device 50A.

[0254] With specific reference to FIG. 24, a sample point adjustmentrequest form 506, according to one embodiment, is shown. In theillustrated embodiment, the point adjustment request form allows theuser 54 to enter the type of points, the number of points, the reasonfor the adjustment, and the player ID card number associated with theplayer 54. When finished, the user 54 may select an ISSUE button to sendthe date to the host computer is where the database 22 is updated.

[0255] With specific reference to FIG. 23B, a second method 510 foradjusting points associated with a player 24 in a player tracking systemis shown. In a first step 512, a request is displayed on the remotedevice 50A. The user 54 may then fill out the form and send the formback to the host computer 18. In one embodiment, a player ID card numberis manually entered on the remote device 59A. In another embodiment, theplayer ID card number is read from the ID card by the bar code reader 66or the ID card reader 62.

[0256] In a second step 514, if a card number was entered, then themethod 510 proceeds to a third step 516. If a card number was notentered, then the method 510 proceeds to a fourth step 516 and an errormessage is displayed. In the third step 516, the card number isvalidated. In a fifth step 518, if the card number is valid then themethod 510 proceeds to a sixth step 520. In the sixth step 520, approvalfor the requested transaction is processed. In a seventh step 522 if theuser or employee 54 has the necessary rights to adjust the player orpatron's points then the method 512 proceeds to an eighth step 524.Otherwise, the method proceeds to the fourth step 516 and an errormessage is displayed. In the eighth step 524, the points are adjustedand the process returns the first step 512.

[0257] K. Comp Point Vouchers

[0258] With reference to FIGS. 25A, 25B and 26, the remote device 50 maybe used to issue point vouchers or comp point vouchers to a player 24.The vouchers may be embodied in a paper voucher which is printed on aremote printer carried by the user 54 or may be embodied in apre-printed voucher having a voucher ID number which is carried by theuser 54, and assigned to the player 24 in the player tracking system.Alternatively, the voucher may be embodied in a record stored in thedatabase 22.

[0259] In one embodiment of the present invention, the remote networkinterface 68 exchanges data between the host computer 18 and the remotedevice 50A. The data includes voucher information to issue a voucher tothe player 24 in the player tracking system. The voucher has at leastone of an associated product and service. For example, the voucher maybe redeemed for the associated product at a related retail store orredeemed for the associated service. Exemplary products includes freedinners and/or drinks.

[0260] As discussed below the remote network interface 68 may send arequest form to the remote device 50A. The user 54 enters data onto therequest form and the remote device sends the data to the remote networkinterface 68.

[0261] With specific reference to FIG. 25, in one embodiment of thepresent invention, a method 530 implements a player tracking system foruse with the gaming system. In a first step 532 a fillable form is sentto the remote device 50A. In a second step 534, the form is filled withdata for issuing a voucher to the player 24.

[0262] The user 54 may enter the player ID card number associated withthe player 24 on the request form. In one embodiment, the player ID cardnumber is entered manually. In another embodiment, the player ID card isread from the player ID card by the ID card reader 62 or the bar codereader 66. After the player has been identified, a list of the vouchersfor which the patron has enough comp points to purchase are listed. Withspecific reference to FIG. 26, a player voucher form 536, according toan embodiment of the present invention, is shown. The player voucherform 536 displays the patron name, the player ID card number, the typeof voucher being selected and the points associated with the patron inthe player tracking system. The player voucher form 536 also lists thevouchers for which the patron may purchase based on the number of comppoints they have.

[0263] With specific reference to FIG. 25B, a flow diagram of a secondmethod 536 for assigning vouchers to a player in a player trackingsystem is shown. In a first step 540, a first request form is displayedon the remote device 50A. The first request form allows the user 54 toselect the type of voucher, i.e., either point or comp point and toenter the card number of the player or patron 24. In a second step 542,if a card number was entered then the process proceeds to a third step546. Otherwise, the method 538 proceeds to a fourth step 544 and anerror message is displayed. In the third step 546, the player's ID cardnumber is validated. In a fourth step 548, if the ID card number isvalid, then the method 538 proceeds to a fifth step 550. Otherwise, themethod 538 proceeds to the third step 544 and an error message isdisplayed. In the fifth step 550, if the player 24 has any points in theplayer tracking system, then the method 538 proceeds to a sixth step552. Otherwise, the method 538 proceeds to the third step 544 and anerror message is displayed. In the sixth step 552, if there are anyactive comps or vouchers that the player 24 can afford based on thenumber of points associated with the player 24 in the patron trackingsystem, then the method 538 proceeds to the seventh step 554. Otherwise,the method proceeds to the third step 544 and an error message isdisplayed. In the seventh step 554, a request form or player voucherform 548 is displayed on the remote device 50A. As discussed above, theplayer voucher form 548 displays a list of vouchers that the player canafford. If the user 54 selects one of the vouchers and selects the issuebutton, then the voucher or comps are issued in the eighth step 556. Ina ninth step 558, if the comp or voucher was issued without errors thenthe method returns to the first step 540. Otherwise, the method returnsto the third step 544 and an error message is displayed.

[0264] L. Redemption of Printed Vouchers

[0265] With reference to FIGS. 27A, 27B and 28, the remote device 50 maybe used to validated and process, i.e., redeem, printed vouchers. Aprinter voucher may be distributed for any number of reasons, forexample, including a promotional event. Typically, the voucher may beredeemed for an associated service or product. For example, a printervoucher may be redeemed for a free dinner or drink.

[0266] As discussed below in one embodiment, the remote networkinterface 68 generates and delivers to the remote device 50A a requestform. The user 54 may enter a voucher ID number onto the form. Bypressing a continue button, the voucher ID may be validated andprocessed. A status may then be returned to the user 54.

[0267] With reference to FIG. 27A, in one embodiment a method 540 isused to redeem a voucher. In a first step 542, a fillable form is sentto the remote device 50A. In a second step 544, the fillable form isfilled out without voucher information by the user 54A. In oneembodiment, the voucher information includes a voucher ID number whichmay be entered manually or by reading a code on the voucher. Forexample, the code may be a bar code printed on the voucher which is readby the bar code reader 66. In a third step 546, the voucher ID number isvalidated and redeemed.

[0268] With specific reference to FIG. 28, in one embodiment, once avoucher has been identified by the remote network interface 68, avoucher information form 548 is displayed on the remote device 50A. Thevoucher information form 548 in the illustrated embodiment includes thevoucher ID number, a good for field which identifies the product orservice for which the voucher may be redeemed, an issued date, and anexpiration date. Once the user 54 verifies the data displayed on thevoucher information form, the user 54 may press the continue button tovalidate and except the voucher.

[0269] With specific reference to FIG. 27B, a method 550 for validatingand processing and redeeming printed vouchers according to anotherembodiment of the present invention is shown. In a first step 552, arequest form is displayed on the remote device 50A. The request formallows the user 54 to enter a voucher number or a voucher ID number. Inone embodiment, the voucher ID number is entered manually. In anotherembodiment, the voucher number is read from the printed voucher. Forexample, the voucher ID number may be encoded into a bar code which isread by the bar code reader 66. In a second step 554, if the voucher IDnumber has been entered then the method proceeds to a third step 556.Otherwise, the method 550 proceeds to a fourth step 558 and an errormessage is displayed. In the third step 556, the voucher number isvalidated. In a fifth step 560, if the voucher number is valid, then themethod proceeds to a sixth step 562. Otherwise, the method proceeds tothe fourth step 558 error message is displayed. In the sixth step 562,if the voucher has already or previously been accepted, then the method550 proceeds to the fourth method step 558 and an error message isdisplayed. Otherwise, the method 550 proceeds to a seventh method step564 and the voucher is marked as accepted within the database 22.

[0270] M. Voucher Information Retrieval

[0271] With reference to FIGS. 29A, 29B and 30, the remote device 50Amay be used to display a list of outstanding vouchers for a selectedplayer or patron 24 and allow the user 54 to accept a specific voucher.Typically the voucher has an associated good, i.e., product, or servicefor which it may be redeemed. For example, a specific voucher may beredeemed for a free dinner and/or drink. In one embodiment, each voucherhas a unique voucher ID number and is stored as a record in the database22. In another embodiment, the voucher may be embodied in a printedticket having the voucher ID printed or encoded thereon. The voucher IDnumber would be associated with the player 24 in the database 22.

[0272] In one aspect of the present invention, at least one voucher isassigned to the player 24 in the player tracking system. The voucher hasat least one of the good and/or service for which it may be exchanged.The remote network interface 68 may be used for exchanging data betweenthe host computer 18 and the remote device 50A. The data includesvoucher information associated with the voucher assigned to the player24 in the player tracking system.

[0273] In one embodiment, the data exchange between the remote device50A and the remote network interface 68 includes a request form. Theremote network interface 68 sends the request form to the remote device50A. The request form may be used by the user 54 for enteringinformation related to the player. The remote device 50A sends theplayer information to the remote interface 68. As discussed below, inone embodiment of the present invention, the player information includesthe player ID card number. The player ID card number may be enteredmanually or may be read by the player ID card reader 62 or the bar codereader 66, as appropriate. The player ID card number is relayed to theremote network interface 68. The remote network interface 68 returns alist of outstanding vouchers associated with the player 24. The user 54may view details related to each voucher. The user 54 may select one ofthe vouchers to accept, i.e., redeem for the associated service or good.

[0274] With specific reference to FIG. 29A, a first method 570 forredeeming outstanding vouchers for a selected player 24 is shown. In afirst step 572, a fillable form is sent to the remote device 50A. In asecond step 574, the form is filled out by the user 54 for identifyingthe player. In a third step 576, voucher information is retrievedthrough the remote network interface 68. As discussed above, once theplayer has been identified, a list of outstanding vouchers is returnedto the remote device 50A. A details button (not shown) associated witheach voucher in the list may be selected by the user 54 to displayvoucher information related to the selected voucher. For example, withreference to FIG. 30, an exemplary voucher information screen 578 isshown. The voucher information screen 578 may display the voucher IDnumber, the good or service for which it may be redeemed, the date itwas issued, and the date the voucher expires. The voucher informationscreen 578 also includes an accept button which may be selected by theuser to accept the voucher as it is redeemed.

[0275] With specific reference to FIG. 29B, second method 580 fordisplaying and redeeming outstanding vouchers associated with the player24 is shown. In a first step 582, a request form is displayed on theremote device 50A. In one embodiment, the user 54 may enter a player IDcard number on the request form. In one embodiment, the player ID cardnumber is entered manually. In another embodiment, the player ID cardnumber may be read from the player ID card by the ID card reader 62 orthe bar code reader 66. In a second step 584, if an ID card number hasbeen entered, then the method 580 proceeds to a third step 588.Otherwise, the method 580 proceeds to a fourth step 586 and an errormessage is displayed. In the third step 588, the ID card number isvalidated. In a fifth step 590, if the ID card number is not valid, thenthe method 580 proceeds to the third step 586 and an error message isdisplayed. Otherwise, the method proceeds to a sixth step 592.

[0276] In the sixth step 592, if the player 24 does not have anyoutstanding vouchers, then the method 580 proceeds to the fourth step586 and an error message is displayed. Otherwise, the method 580proceeds to a seventh step 594.

[0277] In the seventh step 594, any outstanding vouchers associated withthe player 24 are retrieved from the database 22. In an eighth step 596,the retrieved outstanding vouchers are displayed on the remote device50A. As discussed above, each voucher in the list has an associateddetail button (not shown).

[0278] In a ninth step 598, if the detail button for one of the listedvouchers was pressed or selected, then the method 580 proceeds to atenth step 600. Otherwise, the method 580 returns to the first step 592.In the tenth step 600, voucher details for the selected voucher areretrieved from the database 22. In eleventh step 602, the voucherdetails for the selected voucher are displayed on the remote device 50A.In a twelfth step 604, if the accept button for the selected voucher waspressed or selected, then the method 580 proceeds to a thirteenth step606. Otherwise, the method 580 returns to the seventh step 594.

[0279] In the thirteenth step 606, the selected voucher is marked asbeing accepted and the method returns to the seventh step 594.

[0280] N. System Information

[0281] In another aspect of the present invention, the database 22 maystore information related to the remote devices 50, including thecurrent state of the remote device 50. As discussed below, thisinformation may be retrieved and displayed on the remote device 50A, forexample, for purposes of tech support. In one embodiment, the user 54selects the servlet or applet from the menu layer 80. The remote networkinterface 68 produces an HTML form that displays the information relatedto the remote device 50 to the user 54.

[0282] In one embodiment, the data includes information which isassociated with a current client being utilized on the remote device50A. For example, the data may include but is not limited to a TCP/IPaddress of the current client. An HTTP context of the current client forthe current session, an IOP ID of the current client as defined in thedatabase 22 and an IOP name of the current client is defined in thedatabase. IOP or input output point is a designator to represent a pointof data input or output such as a dedicated terminal, hand held device,etc., that is distinguished usually by its IP address on the network.The IOP ID and name are used to tie transactions that are generated to aparticular entity or device.

[0283] The data may also include information related to a current user54 of the remote device 50. For example, the data may include anemployee ID number and/or the employee name.

[0284] Obviously, many modifications and variations of the presentinvention are possible in light of the above teachings. The inventionmay be practiced otherwise than as specifically described within thescope of the appended claims.

What is claimed is:
 1. A remote system for use with a gaming system, thegaming system having at least one gaming machine capable of issuing ajackpot, a host computer coupled to the at least one gaming machine by anetwork, the host computer including a database for maintaining jackpotinformation relating to the at least one gaming device, the remotesystem comprising: a remote device for receiving data; and a remotenetwork interface coupled to the remote device for exchanging the databetween the host computer and the remote device, the data includingjackpot information to process the jackpot.
 2. A remote system, as setforth in claim 1, wherein the remote device is coupled to the remotenetwork interface by a wireless connection.
 3. A remote system, as setforth in claim 2, wherein the wireless connection uses and IEEE 802.11standard.
 4. A remote system, as set forth in claim 3, wherein thewireless connection is IEEE 802.11b.
 5. A remote system, as set forth inclaim 4, wherein the wireless connection is IEEE 802.11g.
 6. A remotesystem, as set forth in claim 1, the remote device having a processorand a web client for interaction with a user.
 7. A remote system, as setforth in claim 6, the web client for acquiring input from the user andformatting and presenting data to the user.
 8. A remote system, as setforth in claim 1, the data including a jackpot form, the remote networkinterface for sending the jackpot form to the remote device.
 9. A remotesystem, as set forth in claim 8, the jackpot form having a jackpot fieldselectable by a user, the remote device for sending the jackpotinformation to the remote network interface located on a host computer.10. A remote system, as set forth in claim 9, the remote device having aprocessor and a web client for interaction with a user, the jackpot formbeing accessible through the web client.
 11. A remote system, as setforth in claim 10, the jackpot form being a web page.
 12. A remotesystem, as set forth in claim 8, the jackpot form being fillable withthe jackpot information by a user, the remote device for sending thejackpot information to the remote network interface.
 13. A remotesystem, as set forth in claim 12, the jackpot information including ajackpot id, the remote network interface for determining if the jackpotid is valid.
 14. A remote system, as set forth in claim 13, the jackpotid inputted manually by the user.
 15. A remote system, as set forth inclaim 14, the jackpot form including a jackpot entry button forselecting by the user and submitting the jackpot id entered manually,the remote device sending a notification that the jackpot entry buttonis selected, the remote network interface for determining if the jackpotid is valid upon receiving the notification.
 16. A remote system as setforth in claim 13, the remote device having a bar code reader forreading a barcode on the jackpot and determining the jackpotinformation, the remote network interface for receiving the jackpotinformation from the bar code reader.
 17. A remote system, as set forthin claim 13, the remote network interface for instructing the remotedisplay to display an error message if the jackpot id is not valid. 18.A remote system, as set forth in claim 17, the remote network interfacefor retrieving jackpot details from the host computer as a function ofthe jackpot id.
 19. A remote system, as set forth in claim 18, thejackpot form including a jackpot button for selecting by the user, theremote device sending a notification that the jackpot button isselected, the remote network interface for storing the notification tothe host computer, the host computer for updating the data in thedatabase.
 20. A remote system, as set forth in claim 1, the hostcomputer including a database for maintaining the jackpot information,the remote network interface coupled to the database for retrieving andstoring data therein.
 21. A remote system, as set forth in claim 20, thedatabase for storing data in database tables.
 22. A remote system, asset forth in claim 21, further comprising a plurality of first dataobjects coupled to the database tables for retrieving and storing datain the database tables.
 23. A remote system, as set forth in claim 22,further comprising at least one second data object coupled to the firstdata objects for assembling multiple first data objects into a thirddata object.
 24. A remote system, as set forth in claim 23, the thirdobject coupled to the remote network interface for receiving queries forthe remote network interface retrieving responsive data from thedatabase formatting the responsive data and returning the responsivedata to the remote network interface.
 25. A remote system, as set forthin claim 24, the remote network interface for receiving the responsivedata and transmitting the responsive data to the remote device.
 26. Aremote system, as set forth in claim 25, the remote device having aprocessor and a web client for interaction with a user, the remotenetwork interface for formatting the responsive data into a hyper textmark-up language response for display by the web client.
 27. A remotesystem, as set forth in claim 26, the web client including a pluralityof servlets for providing functionality to the user.
 28. A remotesystem, as set forth in claim 27, the web client including a login layerfor identifying the user.
 29. A remote system, as set forth in claim 28,the web client including a menu layer for allowing the user to navigateto and access the servlets.
 30. A remote system, as set forth in claim29, the user having an assigned type, the menu layer for allowingaccessing to servlets and restricting access to servlets as a functionof the assigned type.
 31. A remote system, as set forth in claim 9, thejackpot information including a jackpot fill identifier, the remoteinterface for retrieving fill detail from the host computer as afunction of the jackpot fill identifier.
 32. A remote system, as setforth in claim 31, the fill detail including a gaming machine id.
 33. Aremote system, as set forth in claim 31, the fill detail including agaming machine location.
 34. A remote system, as set forth in claim 31,the fill detail including a gaming date.
 35. A remote system, as setforth in claim 31, the fill detail including a gaming shift.
 36. Aremote system, as set forth in claim 31, the fill detail including ajackpot value.
 37. A remote system, as set forth in claim 31, the filldetail including a jackpot status.
 38. A remote system, as set forth inclaim 37, the jackpot status including a request status.
 39. A remotesystem, as set forth in claim 37, the jackpot status including anacknowledge status.
 40. A remote system, as set forth in claim 37, thejackpot status including a process status.
 41. A remote system, as setforth in claim 37, the jackpot status including a paid status.
 42. Aremote system, as set forth in claim 9, the jackpot field including ajackpot identifier.
 43. A remote system, as set forth in claim 9, thejackpot field including a jackpot status.
 44. A remote system, as setforth in claim 42, the remote device sending a notification that thejackpot identifier is selected, the remote network interface forretrieving jackpot detail from the host computer as a function of thejackpot identifier.
 45. A remote system, as set forth in claim 44, thejackpot detail including the gaming machine id.
 46. A remote system, asset forth in claim 44, the jackpot detail including the gaming machinelocation.
 47. A remote system, as set forth in claim 44, the jackpotdetail including the gaming machine game.
 48. A remote system, as setforth in claim 44, the jackpot detail including the gaming machinedenomination.
 49. A remote system, as set forth in claim 44, the jackpotdetail including the gaming date.
 50. A remote system, as set forth inclaim 44, the jackpot detail including the gaming shift.
 51. A remotesystem, as set forth in claim 43, the remote device sending anotification that the jackpot status is selected, the remote networkinterface for advancing the jackpot status via the host computer as afunction of the prior jackpot status, the remote network interfacesending the advanced jackpot status to the remote device.
 52. A remotesystem, as set forth in claim 51, the remote device displaying theadvanced jackpot status.
 53. A method for processing a jackpot for usewith a gaming system, the gaming system having at least one gamingmachine capable of issuing the jackpot, the method including the stepsof: sending a selectable form to a remote device; selecting data fromthe form, by a user, on the remote device for processing the jackpot.54. A method, as set forth in claim 53, the gaming system including ahost computer and a remote network interface for coupling the remotedevice to the host computer, including the step of providing a wirelessconnection between the remote device and the remote network interface.55. A method, as set forth in claim 54, wherein the wireless connectionuses and IEEE 802.11 standard.
 56. A method, as set forth in claim 54,wherein the wireless connection is IEEE 802.11b.
 57. A method, as setforth in claim 55, wherein the wireless connection is IEEE 802.11g. 58.A method, as set forth in claim 54, the remote device having a processorand a web client for interaction with a user, the method including thesteps of: acquiring input via the web client from the user; andformatting and presenting data to the user.
 59. A method, as set forthin claim 53, the data including a jackpot form, the method including thestep of sending the jackpot form to the remote device.
 60. A method, asset forth in claim 59, the data including jackpot information, thejackpot form having a jackpot field selectable by a user, the methodincluding the step of sending the jackpot information to the remotenetwork interface located on a host computer.
 61. A method, as set forthin claim 60, the remote device having a processor and a web client forinteraction with a user, the method including the step of accessing thejackpot form through the web client.
 62. A method, as set forth in claim61, the jackpot form being a web page.
 63. A method, as set forth inclaim 59, the jackpot form being fillable with jackpot information by auser, the method including the step of sending the jackpot informationto the remote network interface located on a host computer.
 64. Amethod, as set forth in claim 63, the method including the step ofconfirming that all required information on the jackpot form was enteredand instructing a display on the remote display an error message if allrequired information was not entered.
 65. A method, as set forth inclaim 64, the jackpot information including a jackpot id, the methodincluding the step of determining if the jackpot id is valid.
 66. Amethod, as set forth in claim 65, including the step of manuallyinputting the jackpot id.
 67. A method, as set forth in claim 66, thejackpot form including a jackpot entry button, the method including thestep of selecting the jackpot entry button.
 68. A method, as set forthin claim 67, including the step of submitting the jackpot id enteredmanually to the remote network interface.
 69. A method as set forth inclaim 68 including the step of sending a notification that the jackpotentry button is selected.
 70. A method, as set forth in claim 69,including the step of determining if the jackpot id is valid uponreceiving the notification.
 71. A method, as set forth in claim 66,including the steps of determining the jackpot id using a bar codereader and transmitting the jackpot id to the remote network interface.72. A method, as set forth in claim 66, including the step ofinstructing the remote display to display an error message if thejackpot id is not valid.
 73. A method, as set forth in claim 53, datarelated to the jackpot processing system being stored in a databasestored on a host computer, the method including the step of providing aremote network interface coupled to the database for retrieving andstoring data therein.
 74. A method, as set forth in claim 73, the methodincluding the step of storing data in database tables.
 75. A method, asset forth in claim 74, the method including the step of providing aplurality of first data object coupled to the database tables forretrieving for retrieving and storing data in the database tables.
 76. Amethod, as set forth in claim 75, the method including the step ofproviding at least one second data object coupled to the first dataobjects for assembling multiple first data objects into a third dataobject.
 77. A method, as set forth in claim 76, the third object coupledto the remote network interface, the method including the steps ofreceiving, by the third object, queries for the remote networkinterface, retrieving responsive data from the database, formatting theresponsive data and returning the responsive data to the remote networkinterface.
 78. A method, as set forth in claim 73, the method includingthe step of receiving, by the remote network interface, responsive dataand transmitting the responsive data to the remote device.
 79. A method,as set forth in claim 78, the remote device having a processor and a webclient for interaction with a user, the method including the steps offormatting, by the remote network interface, the responsive data into ahyper text mark-up language response for display by the web client. 80.A method, as set forth in claim 58, the web client including a pluralityof servlets for providing functionality to the user.
 81. A method, asset forth in claim 80, the web client including a login layer foridentifying the user.
 82. A method, as set forth in claim 81, the webclient including a menu layer for allowing the user to navigate to andaccess the servlets.
 83. A method, as set forth in claim 82, the userhaving an assigned type, the menu layer for allowing accessing toservlets and restricting access to servlets as a function of theassigned type.
 84. A method, as set forth in claim 60, the jackpotinformation including a jackpot fill identifier, the method includingthe step of retrieving, by the remote network interface, fill detailfrom the host computer as a function of the jackpot fill identifier. 85.A method, as set forth in claim 84, the fill detail including a gamingmachine id.
 86. A method, as set forth in claim 84, the fill detailincluding a gaming machine location.
 87. A method, as set forth in claim84, the fill detail including a gaming date.
 88. A method, as set forthin claim 84, the fill detail including a gaming shift.
 89. A method, asset forth in claim 84, the fill detail including a jackpot amount.
 90. Amethod, as set forth in claim 84, the fill detail including a jackpotstatus.
 91. A method, as set forth in claim 90, the jackpot statusincluding a request status.
 92. A method, as set forth in claim 90, thejackpot status including an acknowledge status.
 93. A method, as setforth in claim 90, the jackpot status including a process status.
 94. Amethod, as set forth in claim 90, the jackpot status including a paidstatus.
 95. A method, as set forth in claim 60, the jackpot fieldincluding a jackpot identifier.
 96. A method, as set forth in claim 60,the jackpot field including a jackpot status.
 97. A method, as set forthin claim 95, the method including the steps of sending, by the remotedevice, a notification that the jackpot identifier is selected,retrieving, by the remote network interface, jackpot detail from thehost computer as a function of the jackpot identifier.
 98. A method, asset forth in claim 97, the jackpot detail including the gaming machineid.
 99. A method, as set forth in claim 97, the jackpot detail includingthe gaming machine location.
 100. A method, as set forth in claim 97,the jackpot detail including the gaming machine game.
 101. A method, asset forth in claim 97, the jackpot detail including the gaming machinedenomination.
 102. A method, as set forth in claim 97, the jackpotdetail including the gaming date.
 103. A method, as set forth in claim97, the jackpot detail including the gaming shift.
 104. A method, as setforth in claim 96, the method including the step of sending, by theremote device, a notification that the jackpot status is selected,advancing, by the remote network interface, the jackpot status via thehost computer as a function of the prior jackpot status, sending, by theremote network interface, the advanced jackpot status to the remotedevice.
 105. A method, as set forth in claim 104, the method includingthe step of displaying, by the remote device, the advanced jackpotstatus.